Automated Integration Tests

Description

This PR adds multiple different files/changes that, in all, enable full automated integration tests on each commit.

• Adds an integration job to ci.yaml that runs on a self hosted runner with a flight controller board connected
• Adds a bootloader target to the Makefile that restart a flight controller board into bootloader mode, and adds a gds-integration command that disables the gds website
• Adds a script that triggers the bootloader reset command on Fprime
• Adds a pytest fixture to the integration test suite that automatically starts the gds before running tests, and closing it once they're done
  • Means the gds would need to be closed before tests are ran

How Has This Been Tested?

Integration tests have been ran on the board and work correctly
The self-hosted runner with the integration job has been tested to work correctly locally, although still need to write a proper set-up guide to get a self-hosted runner completely ready

• Unit tests
• Integration tests
• Z Tests
• Manual testing (describe steps)

Screenshots / Recordings (if applicable)

Action Link

Checklist

• Written detailed sdd with requirements, channels, ports, commands, telemetry defined and correctly formatted and spelled
• Have written relevant integration tests and have documented them in the sdd
• Have done a code review with
• Have tested this PR on every supported board with correct board definitions

Further Notes / Considerations